-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
gh-141070: Rename PyUnstable_Object_Dump to PyObject_Dump
#142848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-141070: Rename PyUnstable_Object_Dump to PyObject_Dump
#142848
Conversation
|
Victor and Petr: It wasn't clear to me whether this needed a new C API WG issue -- if you'd like another vote, please let me know. |
|
I reopened capi-workgroup/decisions#87 (comment). |
vstinner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
The C API Working Group approved renaming the function to PyObject_Dump(): capi-workgroup/decisions#87 (comment)
|
See the DPO thread. As a result of my grumpiness (sorry!), the consensus seems to be that it's fine to keep this in the public API, primarily to save typing time when debugging.
📚 Documentation preview 📚: https://cpython-previews--142848.org.readthedocs.build/